Medway Council
Tree preservation zone
There is a problem
- 81 entries must have dates in YYYY-MM-DD format
entity: 19128489
- reference
- G111-1991
- name
- tree-preservation-order
- tree-preservation-zone-type
- geometry
- MULTIPOLYGON (((0.543572 51.393404,0.543549 51.393392,0.543551 51.393373,0.543583 51.393362,0.543612 51.393375,0.543610 51.393394,0.543572 51.393404)),((0.543861 51.393450,0.543845 51.393435,0.543860 51.393415,0.543895 51.393415,0.543911 51.393434,0.543891 51.393452,0.543861 51.393450)),((0.543434 51.393488,0.543448 51.393478,0.543477 51.393474,0.543497 51.393480,0.543506 51.393487,0.543509 51.393505,0.543486 51.393522,0.543450 51.393521,0.543430 51.393502,0.543434 51.393488)),((0.543682 51.393608,0.543669 51.393597,0.543683 51.393580,0.543709 51.393582,0.543718 51.393597,0.543708 51.393607,0.543682 51.393608)))
- point
- POINT (0.543623 51.393467)
- notes
- entry-date
- 2025-10-07
- start-date
- end-date
How to fix this issue
Your dataset is missing the start-date column.
The Tree preservation zone guidance explains how to fix the issue:
start-date
The date that the tree preservation order came into force, written in YYYY-MM-DD format.
Example: 1984-03-28
How to improve Medway Council’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL